home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
rnode10.zip
/
RNODE.DOC
< prev
next >
Wrap
Text File
|
1992-09-23
|
12KB
|
239 lines
RNODE.DOC Page:1
RNODE Version 1.0
RBBS-PC Multinode Take Down Utility
Copyright (C) 1992 Lightning Software, All Rights Reserved
Written And Coded By Robert L. Folmer
***Bear Cat BBS Home Of Lightning Software (404) 739-1216***
Warranty
========
RNODE 1.0 is distributed without warranty. In no event
will Lightning Software be liable to you for any damages from
running this program. Including any loss of profits, lost
savings, or other incidental or consequential damages arising
out of your use of or inability to use the program, even if
Lightning Software or a authorized representative has been
advised of the possibility of such damages.
Lightning Software will not be liable for any such claim by
any other party. All risk associated with using this program
are the complete responsibility of the user.
Introduction - What RNODE Does
==============================
RNODE is a utility for use with RBBS-PC that takes a node down while
another node is currently running an event. The program has many
uses. Taking a node offline during system events is usually a good
idea to do and some events running while any other nodes are running
make it necessary for protection. Some events such as mail runs can
conflict if other nodes are active, and some programs such as message
base packing utilities like MU-PURGE can damage RBBS's data files and
corrupt message bases if ANY nodes are active. As stated earlier, it's
a good idea to take all nodes offline until an event completes, not
only to prevent costly damage, but also to avoid lock ups caused by
sharing violations. Use RNODE and you will be safe. RNODE is designed
to bring RBBS's lines down for system maintnance, and will not place
them back up until the event has completed. RNODE is also a snap to
install and is very easy to use, this next section describes important
installation procedures for RNODE 1.0, please read it carefully before
using RNODE. Please remember that RNODE is released as shareware, you
are free to use the software on your RBBS-PC for a period of 30 days,
after which you must register the software for $10.00 to continue it's
use. We hope that you find RNODE to be a useful RBBS utility, and will
support it's continued development by registering today!
Installation
============
RNODE is designed with ease of installation in mind, the following
shows you step by step how to install and use RNODE...
If you have not done so already, edit your RBBS start up batch file(s)
to change the name of the daily event file in which RBBS invokes,
change all occurances of RBBSTIME.BAT to a name in which you would
RNODE.DOC Page:2
prefer, for clarity we recommend RBBSTM#.BAT where # is the node
number of the batch file you are currently editing. You may name the
file any name you wish, the above is suggested only as an example.
This procedure allows RBBS to run seperate events on each node, which
is required for RNODE to function properly.
1.) Create a directory to hold all of the RNODE files, you may name
the directory what you wish, however for clarity we recommend
RNODE. Next edit your AUTOEXEC.BAT file to include the newly
created directory in your PATH statement, note that this is not
necessary for proper operation, however it does make using the
software much easier. Without RNODE included in the DOS PATH, it
is necessary to either change to the directory containing RNODE's
files, or include the full path to it's files when running the
program.
2.) Uncompress the RNODE distribution archive into the above created
directory. You may now run RNODE to be sure it is working properly
this can be done by entering RNODE at the DOS prompt, typing
RNODE without any parameters specified will display a quick
reference to RNODE's command line format.
3.) Next depending on the number of lines you have, you will need to
create a event to run RNODE on every line other than the one which
is actually running a system event. So the first step would be to
go into RBBS's CONFIG.EXE and hit Shift + F4, this will bring you
to the options for events, net-mail etc. Select option # 261
and enter a time to run RNODE, this time factor is very important,
and requires further explanation, RNODE should be setup as in the
following table, this example is for a 4 node RBBS system:
Node 1 - Runs system event at 0200 (2:00 am)
Node 2 - Runs RNODE event at 0159 (1:59 am)
Node 3 - Runs RNODE event at 0158 (1:58 am)
Node 4 - Runs RNODE event at 0157 (1:57 am)
Notice the time factors in which RBBS is set to exit to DOS, the
reason each node is set 1 before the other, is because if a node
exits at exactly the same time, this may cause problems with RBBS,
such as sharing violations, abnormal termination etc.
4.) The final step to setting up RNODE on the example 4 node system is
to create a batch file for each node to run RNODE, the files
should look similar to the following:
Node 1 Event Batch File - RBBSTM1.BAT
@ECHO OFF
CLS
<event commands>
RBBS1
Node 2 Event Batch File - RBBSTM2.BAT
@ECHO OFF
CLS
RNODE.DOC Page:3
RNODE 120 C:\RBBS\NODE1\RBBS1TM.DEF
RBBS2
Node 3 Event Batch File - RBBSTM3.BAT
@ECHO OFF
CLS
RNODE 180 C:\RBBS\NODE1\RBBS1TM.DEF
RBBS3
Node 4 Event Batch File - RBBSTM4.BAT
@ECHO OFF
CLS
RNODE 240 C:\RBBS\NODE1\RBBS1TM.DEF
RBBS4
The above example may seem rather confusing at first, but actually it
is quite simple....The time factors you tell RNODE and RBBS is the
most important. The numeric digits you give to RNODE is the number of
seconds to delay before going back to check for a signal file, usually
this should be set to a miminum of 2 minutes, then for each additional
node add 1 minute, so for example node 2's batch file delays 2 minutes
(120 seconds) before going back to see if node 1 (the node which is
running the event) has completed, node 3's batch file delays 3 minutes
(180 seconds) before going back to see if node 1's event is done.
If you are running an event on a node other than node 1, simply change
the above batch files to check for a RBBSxTM.DEF file where x is the
node number and the path name to the file appropriately.
Note: The above batch files are included in the RNODE distribution
archive.
Additional Program Notes
========================
The following should cover most questions you may have about RNODE:
Note 1 - RNODE fully supports up to 36 nodes (the maximum number of
nodes RBBS itself supports) and thus locks and unlocks it's
files appropriately.
Note 2 - RNODE will NOT place a node online until the system event for
the node you chose has FULLY completed. In order for this to
function properly, you MUST tell RNODE the correct event
signal file, the example included in this guide show what a
typical setup for RNODE would be on a system which runs the
actual event on node 1.
Note 3 - RNODE as stated earlier is designed for use in "network"
enviroments and multitaskers, it is only necessary to run
RNODE from one copy, what this means is that you can install
multiple copies of RNODE, or simply run one copy. If you are
using one copy, we recommend you mark the RNODE.EXE file
read-only, as this can prevent sharing violations which may
occur when multiple nodes try to access RNODE. This can be
RNODE.DOC Page:4
done with the utility ATTRIB included with DOS, change to
your directory containing the RNODE files and type the
following: ATTRIB +R RNODE.EXE <--This will make your
RNODE.EXE file read-only.
Note 4 - Many people ask the same question "Do I really need to use a
program such as RNODE?". This is entirely up to you, however
it is highly recommended for ANY multi-node system to run
a program such as RNODE to disable ALL nodes while a system
event is running. This can save yourself a lot of work, as it
prevents problems associated with running a program at
the same time, this includes conflicts, sharing violations,
files becoming corrupted, lock-ups - you name it, to be safe
you should run a disable utility like RNODE.
Note 5 - You may install RNODE anywhere you wish, the installation
instructions in this guide are included only as an example,
this gives you complete control over where you want the
RNODE files installed, however for all installation methods
we recommend that you install RNODE in your PATH statement,
as this allows you to run the program from any other
directory, without having to change to the directory in
which RNODE's files are located.
Registration
============
RNODE 1.0 is being distributed under the shareware concept,
you are free to use this product for a period of 30 days after
which you must either register the program or discontinue it's use.
Registration is only $10.00, registering RNODE will get rid of
the UNREGISTERED notices contained in the program. When you register
RNODE you will receive a registered copy of the software on
your choice of 3 1/2" or 5 1/4" disk. As well as a registered key
file that displays your registration number on the main title screen,
the latest version, complete documentation and lifetime support.
To register your copy please complete the included form (REGISTER.FRM)
and return it to the address on the form.
Questions And Or Comments
=========================
If you have questions or comments about this or any other
Lightning Software product, please write to the address below
or call the Lightning Software support BBS (Bear Cat BBS)
at (404) 739-1216 24 hours a day.
Lightning Software
P.O. Box 177
Lithia Springs, Ga 30057